Understand Setups

A setup, in its simplest terms, is the “package” used to install your files and programs onto your user's machine. It is a complete collection of the application files, as well as a component that interacts with the Windows Installer. The primary task of any setup is to transfer the application files from the setup disk to the end user's computer, whether it be a traditional Windows setup or a setup designed to interact with Window Installer. Unfortunately, the complexities of the Windows operating system make it anything but simple to create an effective, coherent setup without the aid of a utility like InstallShield.

Windows Installer Setups

The differences between traditional setups and those created to utilize the Windows Installer lie in Windows architecture. A traditional setup, such as one you may have authored with earlier InstallShield products, requires shipping a custom installation application that interacts with the target system. A Windows Installer setup does not require a separate engine to be shipped. Instead, it interacts with the Windows Installer service that is present on all Windows 2000 machines.

The Windows Installer service eliminates the need for any setup engine to run on the target machine, since the installer service acts as this engine. Therefore, one of its greatest benefits is the fact that all installations will be run through a common engine. This allows the operating system to keep track of all the installation databases. If any necessary files get deleted or corrupted, they can be reinstalled as needed. The many benefits of the Windows Installer service have been outlined in Introduction to Windows Installer .